IPv6 on GitHub-hosted runners #668

BrightRan · 2020-04-03T06:47:52Z

This issue is transferred from here.

In this ticket, the user is trying to reach the IPv6 address of Google by running the command "curl -6 https://www.google.com" on the GitHub-hosted Ubuntu runner, but it always failed to connect and returned the message "Couldn't connect to server".
The command "curl https://www.google.com" or "curl -4 https://www.google.com" can work fine to reach the IPv4 address.

I also tested directly ping the IPv6 address of Google via the command "ping6 ipv6.google.com", it also failed to connect and returned the message "connect: Network is unreachable".

To check whether the current Linux kernel supports IPv6 via the command,

[ -f /proc/net/if_inet6 ] && echo 'IPv6 ready system!' || echo 'No IPv6 support found! Compile the kernel!!'

It returns "IPv6 ready system!", looks like IPv6 is supported.
Then to check whether the IPv6 module has loaded,

lsmod | grep -qw ipv6 && echo "IPv6 kernel driver loaded and configured." || echo "IPv6 not configured and/or driver loaded on the system."

It returns "IPv6 not configured and/or driver loaded on the system.", looks like the IPv6 module is not loaded.
Load the IPv6 module and check again.

modprobe ipv6
lsmod | grep -qw ipv6 && echo "IPv6 kernel driver loaded and configured." || echo "IPv6 not configured and/or driver loaded on the system."

The returned result still shows that the IPv6 module is not loaded. Looks like this should be the reason for failed to reach the IPv6 address.

Why it can't load the IPv6 module on the GitHub-hosted runner? Whether this is an expected behavior for some limitations set on the hosted runners?

The text was updated successfully, but these errors were encountered:

miketimofeev · 2020-04-06T08:28:07Z

@BrightRan looks like the images itself are ok.
@alepauly do we have ipv6 configured on the environment side?

airtower-luna · 2020-04-06T08:36:05Z

According to the Docker documentation the images would still need to enable IPv6 for Docker containers, even if the VMs start to support it.

alepauly · 2020-05-05T14:13:19Z

Unfortunately we can't support this at this time due to infrastructure constraints.

lzhecheng · 2020-08-05T09:23:24Z

Unfortunately we can't support this at this time due to infrastructure constraints.

Is it in the roadmap? I found no opening issues on IPv6 support. Thanks.

miyurusankalpa · 2021-01-08T09:31:23Z

GitHub IP address list now has IPv6 address for GitHub Actions.
https://api.github.com/meta

oscartbeaumont · 2021-01-08T09:36:53Z

As of a week ago, I could not get IPv6 working in GitHub Actions but let's hope them listing those address's means they are about to release support for it.

pavelkim · 2021-01-09T02:27:57Z

Tested today.
Under both ubuntu-latest and ubuntu-20.04:

curl -vv --ipv6 "[2607:f8b0:4002:c03::93]:80"

* Rebuilt URL to: [2607:f8b0:4002:c03::93]:80/
*   Trying 2607:f8b0:4002:c03::93...
* TCP_NODELAY set
* Immediate connect fail for 2607:f8b0:4002:c03::93: Network is unreachable
* Closing connection 0
curl: (7) Couldn't connect to server

ip route sh

default via 10.1.0.1 dev eth0 proto dhcp src 10.1.0.4 metric 100 
10.1.0.0/16 dev eth0 proto kernel scope link src 10.1.0.4 
168.63.129.16 via 10.1.0.1 dev eth0 proto dhcp src 10.1.0.4 metric 100 
169.254.169.254 via 10.1.0.1 dev eth0 proto dhcp src 10.1.0.4 metric 100 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown

ip addr sh

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:0d:3a:c6:7b:12 brd ff:ff:ff:ff:ff:ff
    inet 10.1.0.4/16 brd 10.1.255.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::20d:3aff:fec6:7b12/64 scope link 
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:79:06:ee:ce brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

No IPv6 routes so far.

…ttps://github.com/actions/runner-images/issues/668\#issuecomment-1872487355>)

Still not working out of the box. Research actions/runner-images#668 (comment)

## Flags Changes This adds the proxy-init flag `--iptables-mode` (with possible values `legacy` and `nft`), which supersedes `--firewal-bin-path` and `firewall-save-bin-path` (which still remain supported). Also the `--ipv6` flag has been added (default `true`). After the set of rules run via iptables are processed, if `--ipv6` is true (which is the default), the same set of rules will be run via ip6tables. Analog changes were applied to linkerd-cni as well. ## Backwards-Compatibility This is backwards-compatible with older control planes and upcoming control planes. If `--ipv6` is not passed (and thus defaults to true), this doesn't impact operation even if the cluster doesn't support IPv6; the ip6tables rules are applied but they're innocuous. OTOH if there's no kernel support for IPv6 (which is the case for github runners*) then the ip6tables command will fail but we'll just log the failure and not fail the linkerd-init container (nor the `add` command for linkerd-cni). This avoids having to explicitly set `--ipv6=false`, but it can be set if the user is aware of such limitations and wants to get rid of the errors. ## Testing Improvements The cni-plugin-integration workflow has been simplified by using a matrix strategy, and enhanced by parameterizing the iptables-mode config. ## Linkerd IPv6 Support This allows routing IPv6 traffic to the proxy, but is just the first step towards IPv6/dual-stack support. Control plane and proxy changes will come up next. ## (*) Github Runners IPv6 Support Even though `modinfo` signals support for IPv6, `ip6tables` commands throw modprobe errors. Indeed, according to actions/runner-images#668 support is not there yet. Also, according to actions/runner#3138 there are issues with hosted runners as well, but that might not affect us if we still expose an IPv4 interface to interact with github. Something to take into account when we get to IPv6 integration testing.

This commit introduces the `force-ipv4` GitHub action to address connectivity issues caused by the lack of IPv6 support in GitHub runners. Details: - actions/runner#3138 - actions/runner-images#668 This change solves connection problems when Node's `fetch` API fails due to `UND_ERR_CONNECT_TIMEOUT` errors. Details: - actions/runner-images#9540 - actions/runner#3213 This action disables IPv6 at the system level, ensuring all outging requests use IPv4. Resolving connectivity issues when running external URL checks and Docker build checks. This solution is a temporary workaround until GitHub runners support IPv6 or Node `fetch` API has a working solution such as Happy Eyeball. Detais: - nodejs/node#41625 - nodejs/undici#1531

undergroundwires · 2024-03-29T12:19:43Z

Here's my workaround (open-source and documented) that I hope that can help you too:

privacy.sexy | force-ipv4: GitHub action to use for GitHub workflows.
privacy.sexy | force-ipv4.sh.: Script for general use.

After days of research and trial/error, this is how I got this working:

Create a script called force-ipv4.sh, that configures system to prefer IPv4 over IPv6, call it to configure the machine. It was not easy to find a reliable cross-platform solution and I went Cloudflare WARP for DNS resolution along with some system configurations.
To easily use the script in GitHub workflows, create GitHub action called force-ipv4 and call it in GitHub runners.
Fixes the IPv6 request issues, and you can happily run e.g. fetch API from Node.

Related commit introducing this fix: undergroundwires/privacy.sexy@52fadcd

This commit upgrades Node.js version to v20.x in CI/CD environment. Previously used Node 18.x is moving towards end-of-life, with a planned date of 2025-04-30. In contrast, Node 20.x has been offering long-term support (LTS) since 2023-10-24. This makes Node 20.x a stable and recommended version for production environments. This commit also configures `actions/setup-node` with the `check-latest` flag to always use the latest Node 20.x version, keeping CI/CD setup up-to-date with minimal maintenance. Details: - actions/setup-node#165 - actions/setup-node#160 Using Node 20.x in CI/CD environments provides better compatibility with Electron v29.0 which moves to Node 20.x. Details: - electron/electron#40343 This upgrade improves network connection handling in CI/CD pipelines (where issues occur due to GitHub runners not supporting IPv6). Details: - actions/runner#3138 - actions/runner-images#668 - actions/runner#3213 - actions/runner-images#9540 Node 20.x adopts the Happy Eyeballs algorithm for improved IPv6 connectivity. - nodejs/node#40702 - nodejs/node#41625 - nodejs/node#44731 This mitigates issues like `UND_ERR_CONNECT_TIMEOUT` and localhost DNS resolution in CI/CD environments: Details: - nodejs/node#40537 - actions/runner#3213 - actions/runner-images#9540 Node 20 introduces `setDefaultAutoSelectFamily`, a global function from Node 19.4.0, enabling better IPv4 support, especially in environments with limited or problematic IPv6 support. Details: - nodejs/node#45777 Node 20.x defaults to the new `autoSelectFamily`, improving network connection reliability in GitHub runners lacking full IPv6 support. Details: - nodejs/node#46790

IPv6 in tests is not supported by GitHub Actions (actions/runner-images#668)

github-actions bot added the needs triage label Apr 3, 2020

BrightRan mentioned this issue Apr 3, 2020

IPv6 on GitHub-hosted runners actions/runner#402

Closed

andy-mishechkin added investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: Ubuntu and removed needs triage labels Apr 3, 2020

miketimofeev added Area: Image administration needs eyes labels Apr 6, 2020

alepauly closed this as completed May 5, 2020

alepauly added wontfix and removed needs eyes labels May 5, 2020

maxim-lobanov mentioned this issue May 23, 2020

Cannot resolve localhost to an IPv6 address on ubuntu-latest (all Python versions affected) #929

Closed

5 tasks

rhansen mentioned this issue Jul 4, 2020

Add geturl connectivity unit tests ddclient/ddclient#235

Merged

aojea mentioned this issue Jul 9, 2020

Add IPv6 only KIND deployment to CI matrix. ovn-kubernetes/ovn-kubernetes#1343

Merged

andy31415 mentioned this issue Jul 10, 2020

Attempt to Re-enable the TestInetLayerDNS Unit Test project-chip/connectedhomeip#1541

Closed

na-- mentioned this issue Jul 20, 2020

Fix IPv6 support grafana/k6#1562

Closed

BenLewis-Seequent mentioned this issue Sep 4, 2020

test_support RustPython/RustPython#2179

Merged

sonalkr132 mentioned this issue Sep 19, 2020

Optionally fallback to IPv4 when IPv6 is unreachable rubygems/rubygems#2662

Merged

4 tasks

coolreader18 mentioned this issue Oct 23, 2020

unittest test_support.py Failed RustPython/RustPython#2241

Closed

alpmestan mentioned this issue Nov 25, 2020

make the tests buildable and runnable with cabal and run said testsuites in CI facebookincubator/hsthrift#6

Closed

alexander-akait mentioned this issue Dec 1, 2020

feat: improve host output and fix open webpack/webpack-dev-server#2892

Merged

6 tasks

jfallows mentioned this issue Jan 28, 2021

IPv6 ITs failing in GitHub Actions reaktivity/nukleus-tcp.java#88

Open

ghost mentioned this issue Feb 7, 2021

Runner not ready after timeout during startup-authentication actions/actions-runner-controller#288

Closed

vsafonkin mentioned this issue Feb 17, 2021

getaddrinfo omits IPv6 info on macOS, Windows runners #2705

Closed

7 tasks

titanism mentioned this issue Jan 7, 2024

feat: added support for IPv6 in GitHub Actions upptime/upptime#904

Open

titanism referenced this issue in forwardemail/status.forwardemail.net Jan 7, 2024

feat: added support for IPV6 via WARP (per <upptime/upptime#904> and <h…

fdd91b8

…ttps://github.com/actions/runner-images/issues/668\#issuecomment-1872487355>)

AnandChowdhary mentioned this issue Jan 20, 2024

Error: Unable to resolve action fscarmen/warp-on-actions@v2, unable to find version v2 upptime/upptime#918

Closed

tssurya mentioned this issue Feb 5, 2024

Run ipv6 lane in control plane jobs ovn-kubernetes/ovn-kubernetes#4106

Merged

mikhailkoliada mentioned this issue Feb 25, 2024

Windows Server 2022 runner does not have IPv6 connectivity #9401

Closed

13 tasks

pulsastrix mentioned this issue Mar 8, 2024

Add support for IPv6 networks (on Linux clients) netbirdio/netbird#1459

Merged

25 tasks

alpeb mentioned this issue Mar 12, 2024

Add IPv6/dual-stack support linkerd/linkerd2-proxy-init#350

Merged

This was referenced Mar 16, 2024

error while ssh into ipv6 server. appleboy/ssh-action#146

Closed

ci: enhance GitHub Actions for IPv6 and flexibility appleboy/ssh-action#303

Merged

undergroundwires mentioned this issue Mar 16, 2024

Happy Eyeballs support (address IPv6 issues in Node 17) nodejs/node#41625

Closed

Mischback added a commit to Mischback/mischback.de that referenced this issue Mar 19, 2024

Deactivating the IPv6 test

660ebad

Still not working out of the box. Research actions/runner-images#668 (comment)

This was referenced Mar 20, 2024

GitHub runner cannot send fetch with node, failing with IPv6 DNS error UND_ERR_CONNECT_TIMEOUT actions/runner#3213

Open

Cannot send outbound requests using node fetch, failing with IPv6 DNS error UND_ERR_CONNECT_TIMEOUT #9540

Closed

avsm mentioned this issue May 29, 2024

[Question]: Source code of packages hosted on ipv6 only website ocaml/opam-repository#25954

Closed

StenAL mentioned this issue Jul 7, 2024

2024 updates StenAL/Baltic-stocks#54

Merged

esabol mentioned this issue Jul 17, 2024

Can't use string ("eof") as a SCALAR ref while "strict refs" in use at .../Gearman/ResponseParser.pm line 175. p-alik/perl-Gearman#50

Open

sjberman mentioned this issue Jul 18, 2024

Functional tests for IPv6 Support nginxinc/nginx-gateway-fabric#2238

Closed

6 tasks

azat mentioned this issue Aug 4, 2024

Windows platform supports reading IPv6 addresses for DNS server. libevent/libevent#1701

Merged

manics mentioned this issue Aug 25, 2024

WIP: Can IPv6 work in GitHub actions? jupyterhub/action-k3s-helm#118

Draft

dlste added a commit to GiuseppeArbore/polito-se2-24-18 that referenced this issue Oct 14, 2024

Use IPv4 instead of IPv6 in tests

0b5021c

IPv6 in tests is not supported by GitHub Actions (actions/runner-images#668)

dlste added a commit to GiuseppeArbore/polito-se2-24-18 that referenced this issue Oct 14, 2024

Use IPv4 instead of IPv6 in tests

3e3644f

IPv6 in tests is not supported by GitHub Actions (actions/runner-images#668)

dlste added a commit to GiuseppeArbore/polito-se2-24-18 that referenced this issue Oct 15, 2024

Use IPv4 instead of IPv6 in tests

604a426

IPv6 in tests is not supported by GitHub Actions (actions/runner-images#668)

dlste added a commit to GiuseppeArbore/polito-se2-24-18 that referenced this issue Oct 16, 2024

Use IPv4 instead of IPv6 in tests

0d0e7bb

IPv6 in tests is not supported by GitHub Actions (actions/runner-images#668)

bschimke95 mentioned this issue Nov 8, 2024

Remove IPv6-only on IPv6 only infra test canonical/k8s-snap#768

Merged

electron0zero mentioned this issue Dec 24, 2024

Move from Circle CI to Github Actions prometheus/blackbox_exporter#1341

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

IPv6 on GitHub-hosted runners #668

IPv6 on GitHub-hosted runners #668

BrightRan commented Apr 3, 2020 •

edited

Loading

miketimofeev commented Apr 6, 2020

airtower-luna commented Apr 6, 2020

alepauly commented May 5, 2020

lzhecheng commented Aug 5, 2020

miyurusankalpa commented Jan 8, 2021

oscartbeaumont commented Jan 8, 2021

pavelkim commented Jan 9, 2021

undergroundwires commented Mar 29, 2024

IPv6 on GitHub-hosted runners #668

IPv6 on GitHub-hosted runners #668

Comments

BrightRan commented Apr 3, 2020 • edited Loading

miketimofeev commented Apr 6, 2020

airtower-luna commented Apr 6, 2020

alepauly commented May 5, 2020

lzhecheng commented Aug 5, 2020

miyurusankalpa commented Jan 8, 2021

oscartbeaumont commented Jan 8, 2021

pavelkim commented Jan 9, 2021

undergroundwires commented Mar 29, 2024

BrightRan commented Apr 3, 2020 •

edited

Loading